Files To Deploy

Developing Applications Using The SoftwareShield System > Deploying Licensed Software > Files To Deploy

## Files To Deploy

### Files to deploy when using IronWrapping

Aside from your own software file distribution requirements, the files you must deploy relative to SoftwareShield are:

1. Distributed (compiled) license file (Main License File)

2. Any AXS files that may have been created by the IronWrapping system during compilation.

3. Any Steganographic Alias Files, if you chose to use them.

In general - everything you need will be stored in the "Release" directory created when you run the IronWrap compiler. You may use the contents of this folder for your installers source.

### Files to deploy when not using IronWrapping

Aside from your own software file distribution requirements, the files you must deploy relative to SoftwareShield are:

1. ClientProtector (SSCProtector) server: SSCProt.dll. If you are not using IronWrapping your installer package must register the SSCProt.dll with the Windows system, and (as usual) it can deployed in the directory where you would normally place shared components or dlls. (See your installers documentation for instructions how to register dlls). We recommend that you place the DLL in the System directory and that your installer marks it with Windows as "shared".

2. Distributed (compiled) license file (Main License File)

3. Any Steganographic Alias Files, if you chose to use them.

### Important File Deployment Notes:

Be sure that you deploy the Main License File to the appropriate directory. Although you can choose virtually any directory, for simplicity we recommend that you deploy it to the same directory as the host application executable. (See the StartUp function in the ClientProtector Reference for information about relative vs. absolute paths of the Main License File.)

Note: the Main License File must be deployed on the client machine. It is not supported to deploy the Main License File (or the application itself) to any other machine through either a UNC path or a mapped drive.

If you use a steganographic alias file with your license, your installer package must put the original bitmap file inside the same directory where you chose to place the Main License File. Again - for simplicity, we recommend that you deploy this and the Main License File to the same directory as the host application executable.

Alias Files do not have to be deployed (except steganographic ones, see above). Hidden Alias Files and Registry Alias Files are only created at run-time.